feat: Betterstack Importer by aggmoulik · Pull Request #2016 · openstatusHQ/openstatus

aggmoulik · 2026-03-26T20:24:29Z

Summary

Adds a Better Stack Uptime import provider to the @openstatus/importers package, enabling users to migrate their monitoring setup from Better Stack into OpenStatus.

This is the first importer that can import actual monitors (HTTP checks with URLs, frequency, regions) — the existing Statuspage importer only imports status page data.

What gets imported

Phase	Better Stack Source	OpenStatus Target
Monitors	Uptime monitors (URL, frequency, method, headers, regions)	`monitor` table
Status Page	Status page (company name, subdomain, custom domain)	`page` table
Monitor Groups	Monitor groups	`pageComponentGroup` table
Sections	Status page sections	`pageComponentGroup` table
Incidents	Incidents (with started/acknowledged/resolved timestamps)	`statusReport` + `statusReportUpdate` tables

Field mapping highlights

Frequency: Better Stack seconds (30, 60, 300...) mapped to OpenStatus periodicity enum (30s, 1m, 5m...)
Regions: Better Stack broad regions (us, eu, as, au) mapped to specific Fly regions (iad, fra, sin, syd)
Incidents: Timestamps (started_at, acknowledged_at, resolved_at) converted to synthetic status report updates (investigating → identified → resolved)
Auth: Bearer token (vs Statuspage's OAuth)
Pagination: JSON:API style — follows pagination.next links

Changes

New files (10)

packages/importers/src/providers/betterstack/ — Full provider implementation:
- api-types.ts — Zod schemas for Better Stack API responses
- client.ts — HTTP client with Bearer auth and JSON:API pagination
- mapper.ts — 9 transformation functions (monitor, frequency, regions, status page, incidents, etc.)
- provider.ts — 5-phase import orchestration
- index.ts — Barrel exports
- fixtures.ts — Mock data (3 monitors, 1 group, 1 status page, 2 sections, 3 incidents)
- client.test.ts — 8 tests (endpoints, auth, pagination, errors)
- mapper.test.ts — 25 tests (all mapping functions with edge cases)
- provider.test.ts — 7 tests (validate, phases, filtering)
packages/icons/src/betterstack.tsx — Better Stack icon component
packages/importers/README.md — Package documentation with architecture, pipeline flow, and "adding a new provider" guide

Modified files (6)

packages/importers/src/index.ts — Register betterstack provider in IMPORT_PROVIDERS
packages/importers/package.json — Add ./betterstack and ./betterstack/fixtures export paths
packages/icons/src/index.tsx — Export Better Stack icon
packages/api/src/service/import.ts — Add writeMonitorsPhase(), createProvider() routing, monitor limit warnings, monitors/monitorGroups/sections phase cases
packages/api/src/router/import.ts — Accept "betterstack" provider, betterstackStatusPageId, includeMonitors option
apps/dashboard/src/components/forms/components/form-import.tsx — Better Stack radio button, provider-specific fields, monitors toggle

Test plan

bun test in packages/importers/ — 75 tests pass (40 new + 35 existing)
Manual test with a real Better Stack API token
Verify dashboard form renders both providers correctly
Test preview + import flow end-to-end against local Turso

Signed-off-by: Moulik Aggarwal <qwertymoulik@gmail.com>

vercel · 2026-03-26T20:24:36Z

@aggmoulik is attempting to deploy a commit to the OpenStatus Team on Vercel.

A member of the Team first needs to authorize it.

cubic-dev-ai

2 issues found across 17 files

Prompt for AI agents (unresolved issues)


Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="packages/importers/src/providers/betterstack/provider.ts">

<violation number="1" location="packages/importers/src/providers/betterstack/provider.ts:113">
P2: The monitor-groups fetch + mapping block is copy-pasted identically in both branches of the `if (statusPages.length > 0)` / `else`. Move it after the conditional to eliminate the duplication — `pageId` is already in scope.</violation>
</file>

<file name="packages/api/src/service/import.ts">

<violation number="1" location="packages/api/src/service/import.ts:41">
P2: Unknown provider names silently fall through to `createStatuspageProvider()`. Separate the `default` case to throw an error for unrecognized providers, so misconfigurations fail fast instead of producing confusing downstream errors.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

packages/importers/src/providers/betterstack/provider.ts

packages/api/src/service/import.ts

Signed-off-by: Moulik Aggarwal <qwertymoulik@gmail.com>

Copilot

Pull request overview

Adds a new Better Stack Uptime importer to @openstatus/importers and wires it through the API import pipeline and Dashboard UI so users can preview/run imports (including monitors) from Better Stack into OpenStatus.

Changes:

Introduces a new Better Stack provider (Zod API types, client w/ pagination, mappers, orchestration, fixtures, and tests).
Extends the API import pipeline to support a betterstack provider, monitor imports, and monitor plan-limit warnings.
Updates Dashboard import form and icons to support Better Stack-specific inputs and toggles.

Reviewed changes

Copilot reviewed 17 out of 17 changed files in this pull request and generated 7 comments.

Show a summary per file

File	Description
packages/importers/src/providers/betterstack/api-types.ts	Zod schemas + TS types for Better Stack API resources.
packages/importers/src/providers/betterstack/client.ts	Better Stack HTTP client (Bearer auth, JSON:API-style pagination).
packages/importers/src/providers/betterstack/client.test.ts	Tests for Better Stack client (auth, pagination, errors, parsing).
packages/importers/src/providers/betterstack/fixtures.ts	Shared mock payloads for Better Stack provider tests.
packages/importers/src/providers/betterstack/index.ts	Barrel exports for the Better Stack provider package entry.
packages/importers/src/providers/betterstack/mapper.ts	Mapping functions from Better Stack shapes to OpenStatus insert shapes.
packages/importers/src/providers/betterstack/mapper.test.ts	Unit tests for all Better Stack mappers.
packages/importers/src/providers/betterstack/provider.ts	Provider orchestration (validate + phase generation).
packages/importers/src/providers/betterstack/provider.test.ts	Provider integration tests (phase structure, filtering, resources).
packages/importers/src/index.ts	Registers `betterstack` in `IMPORT_PROVIDERS` and re-exports.
packages/importers/package.json	Adds `./betterstack` and `./betterstack/fixtures` export paths.
packages/importers/README.md	New package-level docs incl. provider architecture and phase mapping.
packages/icons/src/betterstack.tsx	Adds Better Stack icon component.
packages/icons/src/index.tsx	Exports the new Better Stack icon.
packages/api/src/service/import.ts	Adds provider routing, monitor limit warnings, and monitor write phase.
packages/api/src/router/import.ts	Accepts `betterstack` provider + Better Stack-specific inputs and options.
apps/dashboard/src/components/forms/components/form-import.tsx	UI support for Better Stack selection, token help text, status page id, and monitor toggle.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-03-26T20:52:43Z

packages/api/src/service/import.ts

+  // 3. Monitor count limit
+  const monitorsPhase = summary.phases.find((p) => p.phase === "monitors");
+  if (monitorsPhase && monitorsPhase.resources.length > 0) {
+    const maxMonitors = config.limits.monitors;
+    const existingMonitors = await db
+      .select()
+      .from(monitor)
+      .where(eq(monitor.workspaceId, config.workspaceId))
+      .all();
+    const remaining = maxMonitors - existingMonitors.length;
+    if (remaining <= 0) {
+      summary.errors.push(
+        `Monitor limit reached (${maxMonitors}). Upgrade your plan to import monitors.`,
+      );
+    } else if (monitorsPhase.resources.length > remaining) {
+      summary.errors.push(
+        `Only ${remaining} of ${monitorsPhase.resources.length} monitors can be imported due to plan limit (${maxMonitors}).`,
+      );
+    }
+  }


The new monitor limit warning logic in addLimitWarnings() isn't covered by the existing packages/api/src/service/import.test.ts suite (which already tests components/custom-domain/subscribers). Adding tests for the monitors phase warnings (under/over limit, existing monitors) would help prevent regressions.

Copilot · 2026-03-26T20:52:43Z

packages/api/src/service/import.ts

@@ -182,6 +237,18 @@ export async function runImport(config: {
            phase.status = "skipped";
          }
          break;


When targetPageId is falsy (no page created and no pageId provided), the monitorGroups/componentGroups case currently does nothing unless includeComponents === false. That leaves the phase in its original "completed" state even though nothing was written. Explicitly mark the phase as skipped (and ideally update resource statuses) when targetPageId is missing.

Copilot · 2026-03-26T20:52:44Z

packages/api/src/service/import.ts

+          } else if (config.options?.includeComponents === false) {
+            phase.status = "skipped";


Similar to the monitorGroups case: if targetPageId is not set, the sections phase will silently do nothing (unless includeComponents === false), leaving the phase reported as completed. Set phase.status = "skipped" (and update resource statuses) when there is no page to attach groups/sections to.

Suggested change

} else if (config.options?.includeComponents === false) {

phase.status = "skipped";

} else if (

config.options?.includeComponents === false ||

!targetPageId

) {

phase.status = "skipped";

for (const resource of phase.resources) {

resource.status = "skipped";

}

Copilot · 2026-03-26T20:52:44Z

packages/importers/src/providers/betterstack/provider.ts

+      // Monitor Groups → Component Groups (always fetched regardless of status pages)
+      const monitorGroups = await client.getMonitorGroups();
+      const groupResources: ResourceResult[] = monitorGroups.map((g) => ({
+        sourceId: g.id,
+        name: g.attributes.name,
+        status: "created" as const,
+        data: mapMonitorGroup(g, config.workspaceId, pageId),
+      }));
+      phases.push({
+        phase: "monitorGroups",
+        status: "completed",
+        resources: groupResources,
+      });
+
+      // Phase 5: Incidents → Status Reports
+      const incidents = await client.getIncidents();
+      const incidentResources: ResourceResult[] = incidents.map((inc) => ({
+        sourceId: inc.id,
+        name: inc.attributes.name ?? `Incident ${inc.id}`,
+        status: "created" as const,
+        data: mapIncidentToStatusReport(inc, config.workspaceId, pageId),
+      }));
+      phases.push({
+        phase: "incidents",
+        status: "completed",
+        resources: incidentResources,
+      });


run() always emits an incidents phase even when no page context exists (config.pageId is undefined and betterstackStatusPageId filtering yields no status page). In that situation the service layer won't be able to write incidents, but the phase will still be reported as completed. Consider only emitting page-scoped phases (sections/monitorGroups/incidents) when you have a page to attach to, or mark them as skipped with a clear reason in the summary.

Copilot · 2026-03-26T20:52:44Z

packages/api/src/service/import.ts

+  const maxMonitors = limits.monitors;
+  const remaining = maxMonitors - existingMonitors.length;
+
+  if (remaining <= 0) {


If remaining <= 0, writeMonitorsPhase sets phase.status = "failed" and returns, but it does not update individual resource.status values. Since importer providers initially mark resources as created, this can leave the summary claiming monitors were created when none were written. Mark all monitor resources as skipped/failed (with an explanatory resource.error) before returning so the summary accurately reflects what happened.

Suggested change

if (remaining <= 0) {

if (remaining <= 0) {

for (const resource of phase.resources) {

resource.status = "skipped";

resource.error = `Skipped: monitor limit reached (max ${maxMonitors})`;

}

Copilot · 2026-03-26T20:52:44Z

packages/importers/src/providers/betterstack/provider.ts

+    validate: async (config) => {
+      try {
+        const client = createBetterstackClient(config.apiKey);
+        await client.getMonitors();
+        return { valid: true };
+      } catch (err) {
+        return {
+          valid: false,
+          error: err instanceof Error ? err.message : String(err),
+        };


validate() currently calls client.getMonitors(), which fetches all monitor pages due to requestAllPages(). That can be very slow/expensive for accounts with many monitors and makes validation heavier than necessary. Consider validating with a single lightweight request (e.g., fetch the first page only / a dedicated "me" endpoint / limit=1 style request) so validation only checks auth/permissions without pulling full datasets.

Copilot · 2026-03-26T20:52:45Z

packages/api/src/service/import.ts

+  const monitorsPhase = summary.phases.find((p) => p.phase === "monitors");
+  if (monitorsPhase && monitorsPhase.resources.length > 0) {
+    const maxMonitors = config.limits.monitors;
+    const existingMonitors = await db
+      .select()
+      .from(monitor)
+      .where(eq(monitor.workspaceId, config.workspaceId))
+      .all();
+    const remaining = maxMonitors - existingMonitors.length;


In addLimitWarnings(), the monitor limit check loads all existing monitors with .select().from(monitor)...all() just to compute a count. For larger workspaces this is unnecessarily heavy; prefer a COUNT(*) (or a minimal select({ id: monitor.id })) so the warning check stays cheap.

# Conflicts: # apps/dashboard/src/components/forms/components/form-import.tsx # packages/api/src/router/import.ts # packages/api/src/service/import.ts # packages/icons/src/index.tsx # packages/importers/package.json # packages/importers/src/index.ts

vercel · 2026-03-27T13:58:20Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
openstatus-dashboard	Ready	Preview, Comment	Mar 27, 2026 3:00pm
openstatus-status-page	Ready	Preview, Comment	Mar 27, 2026 3:00pm
openstatus-web	Ready	Preview, Comment	Mar 27, 2026 3:00pm

cubic-dev-ai

3 issues found across 13 files (changes from recent commits).

Prompt for AI agents (unresolved issues)


Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="packages/importers/src/providers/betterstack/provider.ts">

<violation number="1" location="packages/importers/src/providers/betterstack/provider.ts:128">
P2: Sequential `await` inside a `for` loop creates an N+1 API call pattern. Each report triggers independent paginated HTTP requests that could run concurrently. With many reports this will be noticeably slow. Consider `Promise.all` (or batch in small groups if rate-limiting is a concern).</violation>
</file>

<file name="packages/api/src/service/import.ts">

<violation number="1" location="packages/api/src/service/import.ts:580">
P2: When `data.type` is `"monitor"` but `sourceMonitorId` is falsy, the fallback to `"static"` is bypassed, potentially inserting a component with `type: "monitor"` and `monitorId: null`. Move the `!data.monitorId` fallback outside the `sourceMonitorId` guard so any unresolved monitor-type component defaults to static.</violation>
</file>

<file name="packages/importers/src/providers/betterstack/mapper.ts">

<violation number="1" location="packages/importers/src/providers/betterstack/mapper.ts:22">
P2: 180 seconds (3 min) is mapped to `"5m"` but is equidistant from `"1m"`. This silently reduces monitoring frequency from every 3 minutes to every 5 minutes for migrated monitors. Consider mapping to `"1m"` instead, which keeps monitoring at least as frequent as the user configured (or introduce a `"3m"` periodicity if supported).</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

packages/importers/src/providers/betterstack/provider.ts

packages/api/src/service/import.ts

packages/importers/src/providers/betterstack/mapper.ts

Copilot

Pull request overview

Copilot reviewed 18 out of 18 changed files in this pull request and generated 4 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-03-27T14:03:20Z

packages/importers/src/providers/betterstack/provider.ts

+        phases.push({
+          phase: "maintenances",
+          status: "completed",
+          resources: maintenanceResources,
+        });
+      } else {


In the status-page branch, the provider never fetches/pushes a monitorGroups phase. This conflicts with the stated Better Stack mapping (monitor groups -> pageComponentGroup) and means monitor groups are only imported when no status page exists. Consider always importing monitorGroups (e.g., fetch once and push the phase regardless of status page presence) so group mappings are available consistently.

Copilot · 2026-03-27T14:03:20Z

packages/api/src/service/import.ts

+  const remaining = maxMonitors - existingMonitors.length;
+
+  if (remaining <= 0) {
+    phase.status = "failed";


When the workspace has no remaining monitor quota, this phase is marked as failed and returns early without marking individual resources. Because overall import status becomes failed if any phase fails, this can make the entire import fail even though other phases (page/components/incidents) could still succeed. Consider marking monitor resources as skipped (with an explanatory error) and setting the phase to completed/partial instead of failed so the rest of the import can proceed cleanly under plan limits.

Suggested change

phase.status = "failed";

for (const resource of phase.resources) {

resource.status = "skipped";

resource.error = `Skipped: monitor limit reached (${maxMonitors})`;

}

phase.status = computePhaseStatus(phase.resources);

Copilot · 2026-03-27T14:03:20Z

packages/api/src/service/import.ts

+  const monitorsPhase = summary.phases.find((p) => p.phase === "monitors");
+  if (monitorsPhase && monitorsPhase.resources.length > 0) {
+    const maxMonitors = config.limits.monitors;
+    const existingMonitors = await db
+      .select()
+      .from(monitor)
+      .where(
+        and(
+          eq(monitor.workspaceId, config.workspaceId),
+          isNull(monitor.deletedAt),
+        ),
+      )
+      .all();
+    const remaining = maxMonitors - existingMonitors.length;


addLimitWarnings loads all existing monitors (.select().all()) just to compute the count. For large workspaces this is unnecessary work and can slow down preview/run. Prefer a COUNT(*) (or equivalent) query so you only fetch the count needed for limit calculations.

packages/importers/README.md

cubic-dev-ai

2 issues found across 8 files (changes from recent commits).

Prompt for AI agents (unresolved issues)


Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="packages/importers/src/providers/betterstack/provider.ts">

<violation number="1" location="packages/importers/src/providers/betterstack/provider.ts:153">
P2: Unbounded `Promise.all` over all reports can fire hundreds of concurrent HTTP requests to the Better Stack API, risking rate-limit (429) errors. Consider batching with a concurrency limit (e.g., `p-limit` or chunked iteration).</violation>
</file>

<file name="packages/importers/README.md">

<violation number="1" location="packages/importers/README.md:10">
P3: The Supported Providers table claims BetterStack imports "maintenances", but the BetterStack phases table below has no `maintenances` phase. This will confuse developers checking what the importer actually supports. Either add the missing phase row or remove "maintenances" from the summary.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

packages/importers/src/providers/betterstack/provider.ts

packages/importers/README.md

aggmoulik added 2 commits March 27, 2026 01:30

Updated BetterStack Importer

306f4fe

Signed-off-by: Moulik Aggarwal <qwertymoulik@gmail.com>

Updated documentation

26603f2

Signed-off-by: Moulik Aggarwal <qwertymoulik@gmail.com>

cubic-dev-ai bot reviewed Mar 26, 2026

View reviewed changes

packages/importers/src/providers/betterstack/provider.ts Outdated Show resolved Hide resolved

packages/api/src/service/import.ts Show resolved Hide resolved

aggmoulik added 3 commits March 27, 2026 01:58

Updated formatting code

b356548

Signed-off-by: Moulik Aggarwal <qwertymoulik@gmail.com>

Fixed the code duplication

868e633

Signed-off-by: Moulik Aggarwal <qwertymoulik@gmail.com>

Update according to the claude review

751ac5c

Signed-off-by: Moulik Aggarwal <qwertymoulik@gmail.com>

mxkaske requested a review from Copilot March 26, 2026 20:46

Copilot started reviewing on behalf of mxkaske March 26, 2026 20:47 View session

Copilot AI reviewed Mar 26, 2026

View reviewed changes

mxkaske added 4 commits March 27, 2026 14:20

fix: format

8d8894d

chore: minor improvements

9286ca0

fix: minor issue

cbd5b11

mxkaske requested a review from Copilot March 27, 2026 13:58

Copilot started reviewing on behalf of mxkaske March 27, 2026 13:59 View session

cubic-dev-ai bot reviewed Mar 27, 2026

View reviewed changes

packages/importers/src/providers/betterstack/provider.ts Outdated Show resolved Hide resolved

packages/api/src/service/import.ts Outdated Show resolved Hide resolved

packages/importers/src/providers/betterstack/mapper.ts Outdated Show resolved Hide resolved

vercel bot deployed to Preview – openstatus-dashboard March 27, 2026 14:00 View deployment

Copilot AI reviewed Mar 27, 2026

View reviewed changes

vercel bot deployed to Preview – openstatus-web March 27, 2026 14:03 View deployment

vercel bot deployed to Preview – openstatus-status-page March 27, 2026 14:05 View deployment

fix: mapper

ede27b4

cubic-dev-ai bot reviewed Mar 27, 2026

View reviewed changes

packages/importers/src/providers/betterstack/provider.ts Show resolved Hide resolved

packages/importers/README.md Show resolved Hide resolved

vercel bot deployed to Preview – openstatus-dashboard March 27, 2026 14:37 View deployment

vercel bot deployed to Preview – openstatus-status-page March 27, 2026 14:39 View deployment

vercel bot deployed to Preview – openstatus-web March 27, 2026 14:42 View deployment

fix: periodicity clamp

7a88244

vercel bot deployed to Preview – openstatus-dashboard March 27, 2026 14:54 View deployment

vercel bot deployed to Preview – openstatus-status-page March 27, 2026 14:56 View deployment

vercel bot deployed to Preview – openstatus-web March 27, 2026 15:00 View deployment

mxkaske merged commit 1f3b54d into openstatusHQ:main Mar 27, 2026
9 checks passed

		} else if (config.options?.includeComponents === false) {
		phase.status = "skipped";

-  if (remaining <= 0) {
+  if (remaining <= 0) {
+    for (const resource of phase.resources) {
+      resource.status = "skipped";
+      resource.error = `Skipped: monitor limit reached (max ${maxMonitors})`;
+    }

Uh oh!

Conversation

aggmoulik commented Mar 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

What gets imported

Field mapping highlights

Changes

New files (10)

Modified files (6)

Test plan

Uh oh!

vercel bot commented Mar 26, 2026

Uh oh!

cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Mar 26, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 26, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 26, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 26, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 26, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 26, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 26, 2026

Choose a reason for hiding this comment

Uh oh!

vercel bot commented Mar 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Mar 27, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 27, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 27, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

aggmoulik commented Mar 26, 2026 •

edited

Loading

vercel bot commented Mar 27, 2026 •

edited

Loading